Arrow keys / Click to navigate

Cloud Operations on AWS

Module 8: Automate Scaling

Cloud Operations on AWS

Module Overview

Scaling with AWS Auto Scaling
Launch templates · Auto Scaling groups · scaling policies
Scaling with Spot Instances
Managing licenses with AWS License Manager

Benefits of Scaling on Demand

Scale out for peak periods · scale in during off-peak
Replace unhealthy instances automatically
Pay only for what you use

Configuring EC2 Auto Scaling

1

Create a launch template (AMI, instance type, security group, key pair)

2

Create an Auto Scaling group

3

Select and configure the scaling policy

Dynamic Scaling Policy Types

Policy	Behavior
Simple scaling	Cycles through cooldown before responding to new alarms
Step scaling	Responds to additional alarms as they occur — recommended
Target tracking	Select a metric and target value; EC2 manages the rest
Predictive scaling	Forecasts load from history and schedules capacity ahead

Avoiding Thrashing

Alarm sustained period — e.g., CPU >90% for 10 minutes
Cooldown period — e.g., suspend scaling for 5 minutes
Instance warm-up period — e.g., 5 minutes before counted in metrics

Spot Instances & Spot Fleets

Cost-effective, price varies with demand for instance type
Requires flexibility — interruptions possible on increased demand
Spot Fleets: set target capacity and max cost per hour

AWS License Manager

Track and manage third-party software licenses
License configuration rules — set hard limits and thresholds
License asset groups for org-wide visibility

Troubleshooting Scenario

Issue: Error: "AMI <AMI ID> is pending, and cannot be run."

Cause: The newly created AMI might not be available yet.

Solution: Wait for the AMI to become available, then create the launch template.

Module Summary

Next: Module 9 — Monitor and Maintain System Health

Module 8 Mind Map

Click branch to expand

1 / 10